Sending failure information from a solid state drive (ssd) to a host device

ABSTRACT

A system, method, and computer program product are provided for sending failure information from a solid state drive (SSD) to a host device. In operation, an error is detected during an operation associated with a solid state drive. Additionally, a command is received for failure information from a host device. Further, the failure information is sent from the solid state drive to the host device, the failure information including failure information associated with the solid state drive.

RELATED APPLICATIONS

The present application is a continuation of U.S. non-provisionalapplication Ser. No. 12/573,792 filed Oct. 5, 2009, now U.S. Pat. No.8,108,737; and wherein the foregoing application is incorporated byreference in its entirety for all purposes.

FIELD OF THE INVENTION

The present invention relates to memory systems, and more particularlyto relaying failure information relating to solid state drives.

BACKGROUND

Currently, when using NCQ (Native Command Queuing) in a Serial ATA(SATA) system and an error occurs, the drive associated with the SATAsystem stops all activity. The drive will continue only when the drivereceives specific information. For example, the drive may continue whenthe drive receives a COMRESET signaling or SRST information from a hostto reset the drive.

As another example, the drive may receive a Read Log Ext 10 command or aRead Log DMA Ext 10 command, where 10 is the page. If the drive receivesa Read Log Ext 10 or a Read Log DMA Ext 10 command, then Log 10 isreturned to the host. This log may include information about the tag ofthe command that failed, a local block address (LBA), and a size of thecommand.

However, in the case of solid state drives (SSDs), the information inthis log is not generally useful. The information in the log does notgenerally contain failure information relevant to an SSD. There is thusa need for addressing these and/or other issues associated with theprior art.

SUMMARY

A system, method, and computer program product are provided for sendingfailure information from a solid state drive (SSD) to a host device. Inoperation, an error is detected during an operation associated with aSerial ATA (SATA) solid state drive. Additionally, a command is receivedfor failure information from a host device. Further, the failureinformation is sent from the solid state drive to the host device, thefailure information including failure information associated with thesolid state drive.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a method for sending failure information from a solid statedrive (SSD) to a host device, in accordance with one embodiment.

FIG. 2 shows a system for sending failure information from a solid statedrive to a host device, in accordance with one embodiment.

FIG. 3 shows a method for sending failure information from a solid statedrive to a host device, in accordance with another embodiment.

FIG. 4 illustrates an exemplary system in which the various architectureand/or functionality of the various previous embodiments may beimplemented.

DETAILED DESCRIPTION

FIG. 1 shows a method 100 for sending failure information from a solidstate drive (SSD) to a host device, in accordance with one embodiment.As shown, an error is detected during an operation associated with aSerial ATA (SATA) SSD. See operation 102.

In one embodiment, the operation associated with the SSD may include anative command queuing (NCQ) operation. In another embodiment, theoperation associated with the SSD may include a non NCQ operation. Forexample, the operation associated with the SSD may include a SATAcommand.

In the context of the present description, an NCQ operation refers toany NCQ operation or command used in the context of a hard disk drive(HDD) or an SSD or a storage device. For example, in one embodiment, theNCQ operation may include sending an NCQ command to an SSD.

Additionally, a command is received for failure information from a hostdevice. See operation 104. The command may include any command that iscapable being used as a request for failure information.

In one embodiment, the failure information may be included in a logpage. In this case, the command for failure information may include arequest for a log page. Of course, the failure information may be in anyform and may not necessarily be included in a log page.

Further, the failure information is sent from the SSD to the hostdevice, the failure information including failure information associatedwith the SSD. See operation 106. The failure information may include anyfailure information associated with the SSD. In various embodiments, thefailure information may or may not be in a log page format. In oneembodiment, the log page may include a log page 10.

Furthermore, the SSD may include any type of SSD. For example, the SSDmay include RAM (e.g. SRAM, DRAM, etc.). In another embodiment, the SSDmay include flash memory. In this case, the flash memory may includenon-volatile flash memory. In various embodiments, the flash memory mayinclude single-level cell (SLC) flash memory and/or multi-level cell(MLC) flash memory. In either case, the SSD may be associated with aSATA system.

The failure information may include any information associated with theerror and/or the SSD. For example, in one embodiment, the failureinformation may include information indicating whether data stored in atleast a portion of the SSD is corrupt. In this case, the error may havecaused the corrupt data or may have been generated by the corrupt data.

In another embodiment, the failure information may include informationindicating a location of the SSD associated with the error. For example,the error may be generated from performing an NCQ operation on aspecific portion of memory associated with the SSD. In this case, thefailure information may indicate the specific portion of memory and anyinformation associated with that portion or the error.

As another example, the failure information may include informationindicating whether the SSD was able to free up space for a commandassociated with the NCQ operation. For example, the NCQ operation mayinclude a command to the SSD to write data or free up space such thatdata may be written. If an error occurs as a result of this command,information associated with that error, including whether the SSD wasable to free up space for the command, may be included in a log page orin another format of returning failing information.

In one embodiment, the failure information may include informationindicating whether the error is associated with a persistent failure ora transient failure. For example, if the error is a reoccurring error,or an error indicative of a reoccurring event, the failure informationmay indicate a persistent failure. If, however, the error is not areoccurring error, or is an error indicative of an anomaly, the failureinformation may indicate a transient failure.

It should be noted that any log page sent as part of the request forfailure information may also include information not necessarilyassociated with the error. For example, in one embodiment, the log pagemay further include information indicating where the SSD is on a lifeexpectancy curve. As another option, the log page may include vendorspecific information. In this case, the vender specific information mayinclude information associated the SSD or a vendor of the SSD.

In another embodiment, the log page may include one or more fieldsassociated with a read log page 10. For example, the log page mayinclude fields and such as device information, logical block address(LBA) information, count information, check sum information, and variousother types of information.

In either case, the failure information and/or the log page may becapable of being utilized to recover failure information associated witha command (e.g. an NCQ command, a SATA command, etc.) issued to the SSD.Additionally, the log page may be capable of being utilized to recoverfailure information associated with a non-queued command issued to theSSD. It should be noted that the command may include any command that iscapable of being used to fetch SSD information to recover from an NCQcommand and any failure information associated with the NCQ command.

Furthermore, the log page may be accessible utilizing a command to fetchSSD failure information. For example, the log page may be accessibleutilizing a Read Log EXT command. As another example, the log page maybe accessible utilizing a Read Log DMA command.

More illustrative information will now be set forth regarding variousoptional architectures and features with which the foregoing frameworkmay or may not be implemented, per the desires of the user. It should bestrongly noted that the following information is set forth forillustrative purposes and should not be construed as limiting in anymanner. Any of the following features may be optionally incorporatedwith or without the exclusion of other features described.

FIG. 2 shows a system 200 for sending failure information from a solidstate drive to a host device, in accordance with one embodiment. As anoption, the present system 200 may be implemented to carry out themethod 100 of FIG. 1. Of course, however, the system 200 may beimplemented in any desired environment. It should also be noted that theaforementioned definitions may apply during the present description.

As shown, the system 200 includes a solid state drive 202 includingmemory 204 and an interface 206 for communicating with a host device208. As shown further, the system 200 may also include a memorycontroller 210. In various embodiments, the memory controller 210 may beincluded with the solid state drive 202 or separate from the solid statedrive 202.

In operation, an error may be detected during an operation beingperformed on the solid state drive 202 (e.g. a native command queuingoperation, etc.). Additionally, a command may be received for a failureinformation (e.g. in a log page format, etc.) associated with the solidstate drive 202 from the host device 208. As a result of this request,the failure information may be sent from the solid state drive 202 tothe host device 208, where the failure information includes failureinformation associated with the solid state drive 202. In this way,useful failure information may be provided in the log page for errorsresulting from commands being sent to the solid state drive 202.

For example, in SATA when using native command queuing and an erroroccurs, the drive stops all activity. The drive will not normallycontinue until the drive receives a COMRESET signaling or an SRSTinformation from a host resetting the drive or the drive receives a ReadLog Ext 10 command, where 10 is the page, or a Read Log DMA Ext 10command.

If the drive receives a Read Log Ext 10 command or a Read Log DMA Ext 10command, then a log 10 page is generally returned to the host. This logmay include information about the tag of the command that failed, LBAinformation, and size of the command, etc.

Table 1 shows an example format of a log page, in accordance with oneembodiment.

TABLE 1 Byte Description 0 Contains NQ bit, UNL bit, NCQ TAG 1 Reserved2 Status 3 Error 6-4 LBA 7 Device  8-10 LBA 11 Reserved 13-12 Count 14-255 Reserved 256-510 Vendor Specific 511 Checksum

To date, however, for an SSD, the information in the log has not beenuseful. For example, in an HDD, the LBA maps to a specific location onthe media that does not change. Every time the host writes the LBA, thisdata goes to the same place. In an SSD, the LBA will go to a differentplace on the media. Thus, the LBA does not inform the host of where thiserror occurred.

As another example, in some cases, an error may occur due to the SSDbeing unable to free up a location on the media to write. This issuedoes not typically exist in HDD systems. HDD systems use this log to getfailure information and decide the appropriate course of action.However, the information in this log does not generally contain failureinformation relevant to a SSD.

Thus, by using this log page or another log page to provide failureinformation that is relevant to an SSD, the log page may be utilized toremedy situations causing errors in the context of an SSD. In variousembodiments, the failure information that is relevant to an SSD mayinclude information indicating whether the data was bad in the flash,the location in the flash, where the drive is on the life curve, whetherthe drive was unable to free up space for the command, whether thefailure is persistent or transient, and various other information.

In this way, a log page 10 may be used to access SSD failure types ofinformation. This log page 10 may be accessed using a Read Log EXTcommand, a Read Log DMA EXT command, or any other commands to fetch SSDfailure information.

The SSD specific information may be vendor specific, or any other fieldsof a Read Log 10 command. Furthermore, a log page may be used to recoverSSD failure information about an NCQ command. Additionally, the log pagemay be used to recover SSD failure information about a non-queuedcommand.

FIG. 3 shows a method 300 for sending failure information from a solidstate drive to a host device, in accordance with another embodiment. Asan option, the present method 300 may be implemented in the context ofthe functionality and architecture of FIGS. 1-2. Of course, however, themethod 300 may be carried out in any desired environment. Again, theaforementioned definitions may apply during the present description.

As shown, it is determined whether an NCQ command, SATA command, orother command is received. See operation 302. If a command is received,it is determined whether an error associated with that command hasoccurred. See operation 304.

If an error has occurred, the error is indicated. See operation 306. Inone embodiment, the error may be indicated by sending an errorindication. In another embodiment, the error may be indicated when aresponse to a command is not received.

It is then determined whether a command for a log page is received. Seeoperation 308. If a command for a log page is received, the log page issent. See operation 310.

If a command for a log page is not received, it is determined whetherreset information is received. See operation 312. If reset informationis received, the SSD is reset. See operation 314.

It should be noted that, in one embodiment, both a reset method or/and acommand for a log page may be received. For example, a command for thelog page may be received and the log page may be sent. Subsequently, areset method may be received. The SSD may then be reset.

FIG. 4 illustrates an exemplary system 400 in which the variousarchitecture and/or functionality of the various previous embodimentsmay be implemented. As shown, a system 400 is provided including atleast one host processor 401 which is connected to a communication bus402. The system 400 also includes a main memory 404. Control logic(software) and data are stored in the main memory 404 which may take theform of random access memory (RAM).

The system 400 also includes a graphics processor 406 and a display 408,i.e. a computer monitor. In one embodiment, the graphics processor 406may include a plurality of shader modules, a rasterization module, etc.Each of the foregoing modules may even be situated on a singlesemiconductor platform to form a graphics processing unit (GPU).

In the present description, a single semiconductor platform may refer toa sole unitary semiconductor-based integrated circuit or chip. It shouldbe noted that the term single semiconductor platform may also refer tomulti-chip modules with increased connectivity which simulate on-chipoperation, and make substantial improvements over utilizing aconventional central processing unit (CPU) and bus implementation. Ofcourse, the various modules may also be situated separately or invarious combinations of semiconductor platforms per the desires of theuser.

The system 400 may also include a secondary storage 410. The secondarystorage 410 includes, for example, a hard disk drive and/or a removablestorage drive, representing a floppy disk drive, a magnetic tape drive,a compact disk drive, etc. The removable storage drive reads from and/orwrites to a removable storage unit in a well known manner.

Computer programs, or computer control logic algorithms, may be storedin the main memory 404 and/or the secondary storage 410. Such computerprograms, when executed, enable the system 400 to perform variousfunctions. Memory 404, storage 410 and/or any other storage are possibleexamples of computer-readable media.

In one embodiment, the architecture and/or functionality of the variousprevious figures may be implemented in the context of the host processor401, graphics processor 406, an integrated circuit (not shown) that iscapable of at least a portion of the capabilities of both the hostprocessor 401 and the graphics processor 406, a chipset (i.e. a group ofintegrated circuits designed to work and sold as a unit for performingrelated functions, etc.), and/or any other integrated circuit for thatmatter.

Still yet, the architecture and/or functionality of the various previousfigures may be implemented in the context of a general computer system,a circuit board system, a game console system dedicated forentertainment purposes, an application-specific system, and/or any otherdesired system. For example, the system 400 may take the form of adesktop computer, lap-top computer, and/or any other type of logic.Still yet, the system 400 may take the form of various other devicesincluding, but not limited to, a personal digital assistant (PDA)device, a mobile phone device, a television, etc.

Further, while not shown, the system 400 may be coupled to a network[e.g. a telecommunications network, local area network (LAN), wirelessnetwork, wide area network (WAN) such as the Internet, peer-to-peernetwork, cable network, etc.] for communication purposes.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example only, and notlimitation. Thus, the breadth and scope of a preferred embodiment shouldnot be limited by any of the above-described exemplary embodiments, butshould be defined only in accordance with the following claims and theirequivalents.

1. (canceled)
 2. A method, comprising: detecting an error during anoperation associated with a solid state drive (SSD); receiving from ahost device a command to return failure information comprising a logpage; and sending the log page from the SSD to the host device inresponse to the receiving, the log page comprising at least one log pagefield comprising information relevant to the SSD being comprised offlash memory as a storage media.
 3. The method of claim 2, wherein theat least one log page field comprises a specific storage media locationof the flash memory where the error occurred.
 4. The method of claim 3,wherein the log page further comprises information indicating whetherthe specific storage media location of the flash memory is associatedwith corrupt data.
 5. The method of claim 2, wherein the at least onelog page field comprises information indicating that the SSD was unableto free up a storage media location of the flash memory in which towrite data for the operation.
 6. The method of claim 2, furthercomprising: wherein subsequent to a determination that the error isassociated with a reoccurring event, the at least one log page fieldcomprises a persistent failure indication; and wherein prior to thedetermination, the at least one log page field comprises a transientfailure indication.
 7. The method of claim 2, wherein the at least onelog page field comprises information indicating where the SSD is on alife expectancy curve.
 8. The method of claim 2, wherein the log page isa Serial ATA (SATA) read log 10 page comprising a vendor specific fieldand the at least one log page field is the vendor specific field.
 9. Themethod of claim 2, wherein the at least one log page field is one ormore of a plurality of fields associated with a Serial ATA (SATA) readlog 10 page.
 10. The method of claim 2, wherein the log page is capableof being utilized to recover failure information associated with an NCQcommand issued to the SSD.
 11. The method of claim 2, wherein thecommand includes a command that is capable of being used to fetch SSDinformation to recover from an NCQ command and failure informationassociated with the NCQ command.
 12. The method of claim 2, wherein thefailure information is accessible utilizing a command other than aSerial ATA (SATA) Read Log EXT command or a Serial ATA (SATA) Read LogDMA command.
 13. The method of claim 2, wherein the failure informationis accessible utilizing a Serial ATA (SATA) Read Log EXT command. 14.The method of claim 2, wherein the failure information is accessibleutilizing a Serial ATA (SATA) Read Log DMA command.
 15. The method ofclaim 2, wherein the log page further comprises a format associated witha Serial ATA (SATA) log page
 10. 16. The method of claim 2, wherein theoperation includes sending an NCQ command.
 17. The method of claim 2,wherein the operation includes sending a SATA command.
 18. A computerprogram product embodied on a tangible computer readable medium,comprising: computer code for detecting an error during an operationassociated with a solid state drive (SSD); computer code for receivingfrom a host device a command to return failure information comprising alog page; and computer code for sending the log page from the SSD to thehost device, the log page comprising at least one log page fieldcomprising information relevant to the SSD being comprised of flashmemory as a storage media.
 19. An apparatus, comprising: a solid statedrive (SSD) configured to: detect an error during an operationassociated with the SSD; receive from a host device a command to returnfailure information comprising a log page; and send the log page fromthe SSD to the host device, the log page comprising at least one logpage field comprising information relevant to the SSD being comprised offlash memory as a storage media.